Project Harness connects Confluence, Jira, Figma, Lucidchart and GitHub, remembers every change, and answers “why is it like this?” with the receipts.
Early access now, lifetime deal on release. No credit card.
Maria is certain the modal stays fullscreen on mobile. You remember a bottom sheet. One of you is about to spend 20 minutes in Confluence proving it.
Bottom sheet below 768px. Spec section “Mobile behaviour”, revised March 4.
git blame points at a developer who left last year. The commit message says “fix checkout”. That is all you get.
the whole story, one answer
You built PROJ-412 exactly as written. The spec had changed nine days earlier. Nobody told you, and the review told everyone.
The linked spec changed since this ticket was written. Section “Checkout — mobile”, revised Aug 24: criterion 3 now requires a saved draft. → view diff
Your AI agent implements the ticket exactly as described. The description is two weeks old. It ships last month’s requirements, fast.
Connect your tools. Thirty minutes, read-only.
Harness backfills your full history from day one.
Ask anything in Slack.
The Harness bot answers in the shared channel, so the whole team sees the answer and the receipts.
Yes. Spec section “Mobile behaviour”, revised March 4. Implemented in PROJ-412, PR #218.
Connect the Harness MCP server to Claude Desktop and Claude Code. PMs ask from Claude Desktop, developers ask without leaving their editor. If your team already runs on Claude, you need nothing else.
Changed in PROJ-412 by Jeppe, PR #218, after the spec revision of Feb 12.
Same memory, same receipts, wherever you ask.
Does the spec say the modal becomes a bottom sheet on mobile?
Yes. Spec section “Mobile behaviour”, revised March 4. Implemented by Jeppe in PROJ-412, PR #218, for breakpoints below 768px.
Every answer cites its sources. When Harness doesn’t know, it says so.
We’re onboarding a small number of teams. You get early access now and a lifetime deal when we release. No call, no commitment. That’s the deal.
We’ll email you when your access is ready.
spec §Mobile behaviour
PROJ-412
PR #218